Remove array-api-strict from 3.10 CI#348
Closed
crusaderky wants to merge 1 commit into
Closed
Conversation
77ebd40 to
9d197ed
Compare
crusaderky
commented
Jul 2, 2025
| NUMPY_VERSION < (1, 26), | ||
| reason="array_api_strict is untested on NumPy <1.26", | ||
| ) | ||
| ) |
Contributor
Author
There was a problem hiding this comment.
numpy 1.26 is the first release with Python 3.12 support
2c28c2e to
d237ce7
Compare
lucascolley
reviewed
Jul 2, 2025
lucascolley
left a comment
Member
There was a problem hiding this comment.
thanks Guido, these changes look good to me if we end up going this way
Member
|
we are going the other way |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is being discussed here data-apis/array-api-strict#160.
It implements option 2/3 in the linked thread.